

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Set Element Templates Package [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Element,Element Templates And Profiles,Element Default Element Template,Element Set Element Template Package,Element Template, Default Element,Element Template Package,Create,Create Element Template,Profile,Profile And Element Templates,Settings,Settings Template Package,Template,Template Package, Settings">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Set Element Templates Package</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="getsetprojectcustomcolors.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="highlightcontextelement.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">In building up a model, you might want to represent or emphasize certain characteristics of elements in the appearance of those elements, or select a particular display option as the standard. For example, you could make new Interface elements a different default color to new Class elements, ensure all new Activity Partitions are vertical rather than horizontal, or set a specific group of display options for new diagrams. You could also define a set of characteristics to use for each development stage of a project.</span></p>
<p class="p_BodyText"><span class="f_BodyText">To do all this, you create a diagram with all the characteristics you require, and store it in an element </span><span class="f_BodyText" style="font-style: italic;">Templates</span><span class="f_BodyText"> package. Enterprise Architect then checks this folder whenever you start to create an element in a diagram and, if it finds a template for that diagram type, applies the settings in that template to the new element or to the display options of the diagram. For example, you could save a diagram under the name </span><span class="f_BodyText" style="font-style: italic;">ClassTemplate</span><span class="f_BodyText">, to apply a set of display characteristics to all new Class elements.</span></p>
<p class="p_BodyText"><span class="f_BodyText">You should create the </span><span class="f_BodyText">Templates</span><span class="f_BodyText"> package in an administrative View of the project file, rather than in any work area. This prevents the package from being changed or lost in any project development work.</span></p>
<p class="p_BodyText"><span class="f_BodyText">There are two other ways in which you can modify the appearance of elements in diagrams:</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">You can define the default appearance of elements (and other structures) grouped in a diagram by using <a href="umlprofiles.htm">UML Profiles</a>. These provide a means of extending the UML Language, which enables you to build UML models in particular domains. They are based on additional stereotypes and Tagged Values that are applied to elements, attributes, methods, connectors, connector ends and so on.</span></li>
<li><span class="f_Bulletlist1">You can modify the appearance of elements (and connectors) of a specific type using <a href="stereotypedlg.htm">stereotypes</a>. Stereotypes take precedence over templates; if you drop an unstereotyped element - a Class, for example - onto a diagram, Enterprise Architect searches the Templates package for a Class diagram that defines an unstereotyped Class, and applies that definition to the new Class. If you drop a stereotyped Class onto a diagram, the stereotype defines the Class appearance so the template is not accessed. Stereotypes are much more flexible for defining the appearance of an element under different scenarios.</span></li>
</ul>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Procedure</span></p>
<p class="p_BodyText"><span class="f_BodyText">To set up the element Templates package, follow the steps below:</span></p>
<ol style="text-indent: 0px; margin-left: 48px; list-style-position: outside;">
<li value=1><span class="f_NumberedList">Create a new package in the appropriate administration View. You can give this package any name; </span><span class="f_NumberedList" style="font-style: italic;">Templates</span><span class="f_NumberedList"> is an unambiguous option.</span></li>
<li value=2><span class="f_NumberedList">Within the </span><span class="f_NumberedList">Templates</span><span class="f_NumberedList"> package create new diagrams, one for each type of diagram to template. Give them easily recognized names; for example </span><span class="f_NumberedList" style="font-style: italic;">ClassTemplate</span><span class="f_NumberedList"> for the template for Class diagrams.</span></li>
<li value=3><span class="f_NumberedList">Add new elements to the template diagrams from the Enterprise Architect UML</span><span class="f_UIControl"> Toolbox</span><span class="f_NumberedList"> and configure the size, appearance, notes, version and other properties.</span></li>
<li value=4><span class="f_NumberedList">Select the </span><span class="f_MenuKeyField">Settings | Template Package</span><span class="f_NumberedList"> menu option to set the templates as the default element templates. The </span><span class="f_UIControl">Browse Project</span><span class="f_NumberedList"> window displays.</span><br>
<span class="f_NumberedList">&nbsp;</span><br>
<img src="elementtemplatebrowse.png" width="276" height="284" border="0" alt="ElementTemplateBrowse"><br>
<span class="f_NumberedList">&nbsp;</span></li>
<li value=5><span class="f_NumberedList">Locate and click on the Templates package, and click on the </span><span class="f_MenuKeyField">OK</span><span class="f_NumberedList"> button to set the package as the default element template.</span></li>
</ol>
<p class="p_BodyText"><span class="f_BodyText">Now each new element you add to your project is created with the settings from the appropriate Template diagram.</span></p>
<div style="text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 5px 0px 5px 13px;"><table cellspacing="0" cellpadding="2" border="0" style="border: none; border-spacing:0px;">
<tr style="text-align:left;vertical-align:bottom;">
<td valign="bottom" width="952" bgcolor="#efeff7" style="width:952px; background-color:#efeff7;"><p class="p_TiporNote" style="border-top: none; border-right: none; border-left: none;"><span class="f_TiporNote">Note:</span></p>
</td>
</tr>
<tr style="text-align:left;">
<td width="952" bgcolor="#f7f7ff" style="width:952px; background-color:#f7f7ff;"><p class="p_TiporNoteText"><span class="f_TiporNoteText">If you decide not to use the default element template, set the default element template to </span><span class="f_MenuKeyField">&lt;none&gt;</span><span class="f_TiporNoteText"> in the </span><span class="f_UIControl">Browse Project</span><span class="f_TiporNoteText"> window.</span></p>
</td>
</tr>
</table>
</div>




            </div>
          </div>
        </div>



</div>


</body>
</html>
